-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apply annotations to default location #3696
Apply annotations to default location #3696
Conversation
@alexkursell please write an e2e test showing the issue. |
I think this should rather be |
After this PR we should DRY this code path - having annotation assignment being duplicated in multiple place is error prone and hard to maintain. |
4d94cb4
to
c226d70
Compare
c226d70
to
7e3304d
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexkursell, ElvinEfendi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Right now, support for ingresses like the following is broken:
While it will route requests for example.com to the service, none of the annotations are applied. This is in contrast to the behaviour of
where the annotations are applied. If we are going to support ingress definitions like the first one here, we should support annotations for them as well.
Which issue this PR fixes
fixes #3520
Special notes for your reviewer:
This PR reverses #1233. I don't have any context as to why that change was made, so if the reasons why are still relevant it would be good to discuss.
cc: @ElvinEfendi , @aledbf